This month's topic: Logging Last Resource (LLR) optimization of XA

Almost every transaction executed on a Java EE Application Server winds up distributed over multiple resources such as JMS destinations and JDBC datasources. Standard OTLP systems employ the XA-2PC protocol, a presumed-abort variant of the Two-Phase Commit protocol to make sure that either all resources commit successfully or all resources abort the transaction if at least one resource fails. As any distributed consensus protocol, XA-2PC is expensive. In this talk, we present Logging Last Resource (LLR) optimization of XA (actually, its Java EE "translation" in form of the JTA spec) in Oracle WebLogic Server. LLR's effectiveness has been validated in world record results achieved by the Oracle stack in the SPECjAppServer2004 benchmark and by high-profile customers in mission-critical applications.

Speaker: Gera Shegalov

Gera has worked in the areas of workflow management, temporal databases, messaging, and recovery. He is currently with Oracle Database High Availability. In his prior role at Oracle, he was part of the Java Platform Group where he worked on the messaging infrastructure such as OC4J JMS, AQ JMS integration, WebLogic FileStore, and LLR. Prior to joining Oracle, Gera worked at the Max Planck Institute of Informatics in Saarbruecken, Germany and interned at Microsoft Research in Redmond, WA.

PJUG meetings start with some time to eat and socialize (pizza and beverages are provided), followed by the featured speaker, then Q&A, discussion, sometimes a drawing to give away swag. :)

Though we like knowing how many people to expect, you don't have to RSVP, on Upcoming or otherwise. Go ahead and just show up!

Many people also go for a drink and further discussion following the meeting, at a location determined ad hoc (lately, Trees restaurant in the same building).

http://twitter.com/pjug http://pjug.org/ (join our mailing list, linked from the website!)

In this talk, we will cover the basics of how to connect an Android device to a MySQL database. The technique used is adaptable to any database server (SQL Server, PostGRES, etc...)

As you probably know, Android does not have a built in functionality to access remote databases, instead it uses SQLLite, a flat file system.

However, using Java EE 7 and a simple PHP connectivity script, it is practically trivial to do the basic CRUD operations on a remotely hosted database.

Bring a laptop with Java 7 and Android SDK with Eclipse installed, and get ready to code. Or just bring yourself, and a sheet will be passed to have the connection code EMAILED to you after the venue.

About the speaker: Sean Walsh (aka Azadi) is the current vice chair of the Portland State Chapter of the ACM. Sean is currently finishing his Bachelor's of Computer Science with a Mathematics Minor at Portland State University, and has industry experience with deploying mobile apps for Android.